home *** CD-ROM | disk | FTP | other *** search
Text File | 1993-04-28 | 204.0 KB | 5,246 lines |
-
-
-
-
-
-
-
- EditRand(tm)
-
-
- A Data File Management Tool
-
-
-
-
-
-
- Written and copyright by
-
- Scott Whitehead
- CMD DATA SERVICES
- 10413 Firethorn Lane
- Austin, Texas 78750-1740
- Compuserve ID 70701,2123
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- SYSTEM REQUIREMENTS:
-
- IBM PC/XT/AT/PS2 or 100% compatible
-
- DOS 3.0 or higher
-
- 400K available RAM
-
- Hard disk or floppy disk
-
- Color or monochrome monitor
-
-
-
-
-
-
-
-
-
-
-
-
- Copyright
-
- Copyright CMD Data Services, 1988-1993. All rights reserved. No part
- of this manual may be reproduced or transmitted in any form or by any
- means, electronic or mechanical, including photocopying and recording,
- for any purpose other than the purchaser's personal use without the
- written permission of CMD Data Services.
-
-
-
-
- Software License Notice
-
- Information in this document is subject to change without notice and
- does not represent a commitment on the part of CMD Data Services. The
- software described in this document is furnished under a license
- agreement or non-disclosure agreement. The software may be used only
- in accordance with the terms of the agreement.
-
-
-
-
- Licenses and Trademarks
-
- EDITRAND is a trademark of CMD Data Services. dBASE is a registered
- trademark of Borland International. Microsoft is a registered
- trademark of Microsoft Corporation. All other brand and product names
- are registered trademarks of their respective companies.
-
-
-
-
- CMD Data Services Software License Agreement
-
- READ THIS LICENSE AGREEMENT BEFORE USING THIS SOFTWARE. By using this
- software, you are accepting the terms of this agreement. If you do
- not accept the terms of this agreement, you may return this entire
- package, including all supplied disks and documentation, within 10
- days for a full refund.
-
- You may use this software on any computer, provided you have physical
- possession of the accompanying original documentation at all times
- during the use of the software. You may not temporarily transfer
- possession of the CMD Data Services software or the right to use the
- software to another individual. You may permanently transfer the
- software to another individual if all original materials, including
- disks and backup copies of the disks, and documentation are delivered
- to the transferee. You may terminate this license at any time by
-
-
-
-
-
-
-
- destroying all original materials as well as all backup copies of the
- software.
-
- You may transfer the software to a single floppy disk or single hard
- disk for the purpose of using the software. You may make two (2)
- backup copies of the software for security purposes.
-
-
-
-
- Limited Warranty
-
- This program assumes the user is thoroughly knowledgeable with DOS
- operations and the particular data that is edited, and that steps will
- be taken to prevent accidental loss of data by maintaining separate,
- timely backups. Every effort has been made to assure that this
- program satisfies the expressed goal of editing random data files.
- However, the Shareware evaluation (trial use) version is provided AS
- IS. CMD Data Services MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR
- IMPLIED, INCLUDING WITHOUT LIMITATION, ANY WARRANTIES OF
- MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE.
-
-
-
-
- Additional Information
-
- You should read the files README.DOC, WARRANTY.DOC, LICENSE.DOC, and
- SHR-WARE.DOC supplied with the software. It contains other important
- information about EDITRAND and shareware. README.DOC may include any
- additional information that did not make it into the documentation
- before it went to the printer. The supplied disk also contains soft
- copies of the forms found in Appendix B of this manual, such as the
- EDITRAND Bug Report/Enhancement Request Form. Such forms have the
- extension .FRM. You can print copies of these forms for your use.
-
-
-
- * * * * * * * * * * * * * * * * * * * * * * * *
-
-
-
- WARNING
-
- EDITRAND is intended to be used with files that are evenly blocked,
- that is, whose total file size is evenly divisible by the user-
- specified record size. Although EDITRAND is capable of browsing and
- editing any DOS file, please be cautious since it is possible to alter
- the length of a file using EDITRAND, such as with the APPEND or DELETE
- record operations. Such an operation on a data file with a
- proprietary format or an executable (.EXE or .COM) could render it
- useless.
-
-
-
-
-
-
-
- REMEMBER: IT IS POSSIBLE TO DESTROY ANY DOS FILE WITH THE EDITRAND
- PROGRAM IF THE EDITRAND USER IS NOT INTIMATELY FAMILIAR WITH THE DOS
- OPERATING SYSTEM AND FILE STRUCTURES.
-
- It is strongly advised that any user of the EDITRAND program read this
- entire manual before attempting to use the program.
-
-
-
-
-
- Be sure to read the tutorial in Appendix C in the back of the
- manual.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- EDITRAND Customization
-
- If you have special editing requirements that EDITRAND does not
- address, CMD Data Services also provides customization of the EDITRAND
- program. For example, EDITRAND could be tailored to:
-
- 1. Intelligently load and handle specified
- proprietary data file formats.
-
- 2. Handle alternate character sets.
-
- 3. Generate indexes or format/prefill records and
- fields to specification.
-
- 4. Perform any specific editing through a defined
- function key or other triggering mechanism.
-
- If interested, please submit a letter of intention, outlining your
- requirements to:
-
- Scott Whitehead
- CMD Data Services
- 10413 Firethorn Lane
- Austin, TX 78750-1740
-
- Please include a summary technical description of your requirements.
- An immediate response will be sent to verify that your request has
- been received, and a detailed response, including cost estimates, will
- be forthcoming 2 to 4 weeks later.
-
-
- * * * * * * * * * * * * * * * * * * * * * * * *
-
- EDITRAND Support
-
- For technical assistance with EditRand, the preferred channel is on
- Compuserve, ID 70701,2123. Email is checked several times a week, and
- more thought can be given to questions and concerns before responding
- in this way.
-
- For licensing or customization questions, or technical questions from
- registered customers, call 512-335-0579. For a bug report or
- enhancement request, it is preferable to fill out and send the
- supplied Report Form (see Appendix B).
-
- NOTE: Technical assistance will NOT be given to UNREGISTERED users on
- the phone, but I will answer any and all questions from anyone on
- Compuserve.
-
-
-
-
-
- EditRand
- ------------------------------------------------------------
-
- Table of Contents
-
- INTRODUCTION.............................................1
- WARNING/DISCLAIMER.......................................4
- INSTALLATION.............................................4
- EXECUTING EDITRAND, switches.............................6
- BROWSE MODE, description................................14
- SUMMARY OF BROWSE MODE FUNCTIONS........................17
- BROWSE MODE FUNCTIONS...................................18
- LOAD new file to be edited............................18
- FILE SELECTION WINDOW...............................21
- EDIT the current record...............................23
- FETCH next or previous record.........................23
- FETCH first or last record in file....................23
- FETCH absolute record.................................24
- FETCH relative record.................................24
- COUNT word occurrences................................24
- COUNT next word occurrences...........................24
- SEARCH for a string...................................24
- SEARCH for NEXT string occurrence.....................24
- FETCH record via absolute byte number.................25
- INVERSE video rule lines..............................25
- BOUNDS - Change string operation boundaries...........25
- ABORT program, lose changes and update ER.INI.........25
- QUIT program, save changes and update ER.INI..........26
- EDIT MODE...............................................27
- SUMMARY OF EDIT MODE FUNCTIONS..........................28
- Basic Navigation Functions............................31
- GO to adjacent characters...........................31
- GO to next or previous tab position.................31
- GO to first or last character within Field Bounds...31
- FETCH next or previous record.......................31
- FETCH first or last record in file..................31
- FETCH record via absolute byte number...............31
- Primary String Functions..............................33
- COUNT word occurrences..............................33
- COUNT word occurrences, repeat......................33
- SEARCH for a string.................................34
- SEARCH for NEXT string occurrence...................34
- REPLACE string......................................35
- REPLACE NEXT repeat previous REPLACE command........39
- Record Functions......................................40
- CUT field bounds string into scratchpad.............40
- PASTE scratchpad into currently displayed record....40
- APPEND new record...................................41
- DELETE record.......................................42
- UNDELETE record or UNDO changes.....................43
- ------------------------------------------------------------
- i
-
-
-
-
-
- EditRand
- ------------------------------------------------------------
-
- Table of Contents
-
- DELETE RANGE of records.............................43
- DYNAMIC Field Boundaries............................45
- Change COLOR of record area.........................45
- CASE Alter..........................................46
- FIND deleted record.................................47
- SORT on field bounds interval.......................47
- Editing Functions.....................................49
- TEXT/HEX entry mode.................................49
- BINARY NUMBER.......................................49
- DISPLAY BINARY NUMBER...............................50
- TAB stop on/off.....................................50
- TAB increment.......................................52
- TAB toggle tab stops off/on.........................53
- TAB stops reset to null.............................53
- BOUNDS change.......................................54
- BOUNDS Reset........................................55
- CLEAR field bounds..................................55
- CLEAR to end of record..............................55
- UPDATE dBASE Header Record Count....................55
- Miscellaneous Functions...............................56
- SAVE AS to another file.............................56
- INVERSE video rule lines............................58
- EXIT to Browse mode.................................58
- PURGE DELETIONS.....................................58
- TOGGLE prompt to purge deleted records..............59
- APPENDIX A - Ancillary String Functions...............60
- APPENDIX B - EDITRAND Forms...........................62
- APPENDIX C - EDITRAND Tutorial........................63
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ------------------------------------------------------------
- ii
-
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
-
-
- INTRODUCTION
-
-
-
- EDITRAND is a utility that allows the user to browse and
- edit any data file containing records of static, equal
- length. Most high level programming languages create this
- type of data file, and is typically referred to as a RANDOM
- file. This is due to the fact that any record can be
- accessed randomly, or directly, without the need to process
- the entire file searching for the desired record. Also,
- data files created by many database systems (such as dBASE
- III) can be handled by EDITRAND, even if they have a
- proprietary header (see page 9).
-
- Each record is displayed with underlying rules to allow easy
- field and byte level checking. One record at a time is
- displayed in its entirety, along with pertinent information
- such as absolute record number, absolute and relative byte
- position, record and field boundaries, header offset, and
- hex/decimal representation.
-
- EDITRAND can be used to analyze random data in ways not
- possible using the program that created the data. Using
- EDITRAND, data can be viewed exactly as it exists on disk,
- allowing speedy verification of program output and
- intelligent troubleshooting of problem situations. Avoid
- long hours of testing - use EDITRAND to peek at those random
- files and find the exact fields and records that are
- suspected of being corrupt or invalid. Have you found that
- an application will not allow a change that is desired?
- Load the data file into EDITRAND, swiftly make the desired
- changes, and put the data back into operation without a
- lengthy waiting period.
-
- EDITRAND can be used to operate on any random data file.
- Key features:
-
- * Browse and edit random data files produced by any
- program, regardless of record structure.
-
- * Display an entire record on the screen at one
- time.
-
-
- ----------------------------------------------------------------------
- Introduction Page 1
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
-
- * Determine exact location of data fields with the
- use of ruled display and user definable tab stops.
-
- * Full text, hexidecimal, binary numeric and ASCII
- data editing.
-
- * Flat data files, data files with any proprietary
- header, or dBASE III format files.
-
- * Cursor key navigation just like ordinary text
- editors.
-
- * Perform standard editing functions such as Search,
- Replace, Word Count, Cut and Paste.
-
- * Perform record functions such as Append, Delete,
- Copy, Move and Sort.
-
- * Full featured binary number operations (IEEE or
- Microsoft Binary Format).
-
- * Restrict operations to a range of records and/or
- range of columns (this allows the user to focus
- operations on a particular data field)
-
- * Expand or collapse record size by inserting or
- deleting a new field anywhere in the record
-
- * Undelete/Undo changes to records
-
- * Create backup files for security purposes
-
- * On line help screen showing all defined function
- keys
-
- * Works on files up to 2 gigabytes in size
-
- * Maximum record length is:
-
- ˛ 1600 bytes per record in standard 80 X 25 text
- mode,
-
- ˛ 3040 bytes per record in 80 X 43 mode (EGA
- required),
-
-
- ----------------------------------------------------------------------
- Introduction Page 2
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
-
- ˛ 3600 bytes per record in 80 X 50 mode (VGA
- required).
-
-
-
- Edit entry operations include standard text, hex, binary
- (string to binary number conversion), and full ASCII entry.
- String operations include Search, Search NOT, Search Next,
- Replace, Replace Global, Replace w/Confirm, Word Count, and
- Word NOT Count performed in text, hex, binary numeric or
- ASCII; also strings may be cut into a scratchpad to be
- inserted (pasted) elsewhere. In addition records may be
- copied, moved, deleted, appended, and sorted.
-
- Central to most string operations is the concept of Bounds,
- which allows the user to focus on a range of records and a
- particular field across the range of records. By confining
- a string operation to such Bounds (such as Replace or
- Search), all strings outside the Bounds will be ignored.
- See the section on Bounds on page 54.
-
- The primary goal of this program is to be able to operate on
- random data files of unlimited size, so that the ability to
- edit a particular file is not dependent upon available
- Random Access Memory to store it in during the edit session.
- Therefore, this program edits directly to disk. This
- naturally presents an element of danger since changes made
- in this manner cannot be directly undone or aborted. To
- overcome this situation, a backup of the edited file is
- created from which record changes are undone and through
- which an entire edit session can be aborted. This backup is
- named by stripping off the name of the file to be edited,
- and giving it the extension .ERB. For example, the input
- file ACCOUNTS.DAT would cause the backup file ACCOUNTS.ERB
- to be created. If there is not enough disk space for the
- backup file, the program will terminate with an error
- message. Also, the sort function requires no additional RAM
- or disk space, as it sorts the main working file directly on
- disk after removing any deleted records. Sorting in this
- manner is typically slow, but again assures the user that
- file size is not an issue.
-
-
-
-
-
- ----------------------------------------------------------------------
- Introduction Page 3
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
- WARNING - PLEASE READ: EDITRAND is intended to be used with
- files that are evenly blocked, that is, whose total file
- size is evenly divisible by the user-specified record size.
- This typically means random data files. For example, any
- file created as RANDOM by the BASIC programming language, or
- as a file of Records in C or Pascal. Although EDITRAND is
- capable of browsing and editing any DOS file, please be
- cautious since it is possible to alter the length of a file
- using EDITRAND, such as with the APPEND or DELETE record
- operations. Such an operation on a data file with a
- proprietary format or an executable (.EXE or .COM) would
- render it useless.
-
- REMEMBER: IT IS POSSIBLE TO DESTROY ANY DOS FILE WITH THE
- EDITRAND PROGRAM IF THE EDITRAND USER IS NOT INTIMATELY
- FAMILIAR WITH THE DOS OPERATING SYSTEM AND FILE STRUCTURES.
-
- It is strongly advised that any user of the EDITRAND program
- read this entire manual before attempting to use the
- program.
-
-
-
- DISCLAIMER: This program assumes the user is thoroughly
- knowledgeable with DOS operations and the particular data
- that is edited, and that steps will be taken to prevent
- accidental loss of data by maintaining separate, timely
- backups. Every effort has been made to assure that this
- program satisfies the expressed goal of editing random data
- files. However, the software and documentation have been
- provided "as is." No warranty is made by the author whether
- expressed or implied. Fitness for any task is solely
- determined by the user.
-
-
-
-
-
-
-
-
-
- INSTALLATION
-
-
-
-
- ----------------------------------------------------------------------
- Introduction Page 4
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
-
- To install EDITRAND, simply copy the file ER.EXE onto a
- working diskette or hard drive, depending upon your
- particular needs. In order that EDITRAND may be executed
- from any drive or subdirectory, make sure that the current
- PATH environment variable contains the subdirectory in which
- ER.EXE is installed.
-
- Be aware that EDITRAND will create its defaults file ER.INI
- in the current default subdirectory any time it is executed.
- This is to allow customized settings for particular files or
- sets of files. For more information, see page 13.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ----------------------------------------------------------------------
- Introduction Page 5
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
- EXECUTING EDITRAND
-
-
-
- EDITRAND can be executed two ways - by passing as arguments
- the name and record length of the desired file, or by simply
- executing with no arguments. When EDITRAND is exited, an
- initialization file called ER.INI is created within the
- current working subdirectory. This file contains various
- items of information about the previous edit session, such
- as file name and record length. It is this initialization
- file that makes it possible to execute EDITRAND with no
- arguments - the previously edited file will be reloaded
- using the same record length and general operating
- environment. There are two methods of executing EDITRAND:
-
- Method one: ER filename recordlength [switches]
-
- Method two: ER [switches]
-
- The first time EDITRAND is executed method one will have to
- be used since there will be no initialization file present.
- Also, (if ER.INI is present) EDITRAND may be executed
- passing only the filename, in which case the record length
- used in the previous session (as found in ER.INI) will be
- used. The EDITRAND user must determine the proper record
- length used by EDITRAND. EDITRAND will not try to guess the
- correct record length, except to default to 1600 bytes if
- ER.INI is not found and no record length is specified.
-
- Several command line switches are available when executing
- EDITRAND:
-
- /N No Backup - Prevent a backup from being created.
- This switch is available if you need to edit a
- file but do not have sufficient disk space to
- create a backup. Use this switch with GREAT
- CAUTION as any changes made are permanent as soon
- as the changes are made:
-
- YOU CANNOT ABORT FROM AN EDIT SESSION
- THAT IS STARTED WITH THE /N COMMAND LINE
- SWITCH. ANY CHANGES YOU MAKE WILL BE
- PERMANENT.
-
-
-
- ----------------------------------------------------------------------
- Executing Page 6
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
- [A warning message is displayed on the bottom line]
-
- For this reason, it is advisable that you make a
- separate backup (perhaps onto floppy disk) of the
- file to be edited prior to executing EDITRAND with
- the /N switch.
-
-
- /B Browse Only - This is a variation of the /N switch
- without the danger involved. Use of the /B
- command line switch prevents a backup from being
- created but also disables edit mode. (Note that
- the browse mode function prompts on the bottom
- line and the help screen [Alt-H] are modified to
- reflect the lack of edit capabilities.) The /B
- command line switch should be used when it is only
- desired to verify the contents of a file without
- the need for alteration.
-
- /E Erase Backup files - This command line switch will
- erase backup files after the session is finished
- with them. Backup files have the extension .ERB.
- Backup files will continue to be made for undelete
- and edit abort purposes, but will be deleted as
- different files are Loaded or when EDITRAND is
- exited. This means that although a file can be
- rescued from unintentional changes before ending
- its session, restoring a file after its session is
- ended is impossible since its backup will have
- been erased by EDITRAND.
-
- The above switches /N, /B, and /E are mutually
- exclusive; only one at a time can be used. If
- more than one is specified, only the first is
- honored.
-
-
-
-
-
-
-
-
-
-
-
-
- ----------------------------------------------------------------------
- Executing Page 7
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
- /M Use Microsoft Binary Format - The default binary
- numeric representation is IEEE. If you wish to
- use the older MBF representation use this switch.
- The string MBF will appear on the left of the
- status line. Please note that the binary format
- utilized by the application program used to
- maintain the data should be used when editing such
- files. In other words, if the parent application
- uses MBF format and you make changes to its data
- file using the default IEEE format, the next time
- the application accesses such an altered number,
- it will NOT be the value intended but something
- entirely different. This point does not apply to
- numeric fields that are maintained in pure ASCII
- format.
-
- /I Use IEEE numeric format. Since IEEE format is the
- default format, the /I switch has effect only when
- loading a file after starting EDITRAND (using the
- "L" command), and the previous mode was MBF as
- imposed by the /M switch.
-
- /D[T] Load File as dBASE III. This switch will cause
- EDITRAND to load the specified files as a dBASE
- III file. This causes the following effects:
-
- 1. The dBASE header is treated as an
- offset, the same as would occur if
- you used the /O switch.
-
- 2. The dBASE record length is used as
- the EDITRAND record length. After
- loading, you should see only one
- dBASE record at a time on the screen.
-
- Once a file has been loaded as a dBASE III file,
- EDITRAND will attempt to load all subsequently
- loaded files as dBASE III files. To switch off
- dBASE mode, use the /On switch (/O0 for zero
- offset is also legal.)
-
-
-
-
-
-
-
- ----------------------------------------------------------------------
- Executing Page 8
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
- [T] This optional switch will cause EDITRAND
- to read the field definitions from the dBASE
- header, and set the EDITRAND tabs to these fields.
- This will cause any previous tab definitions to be
- lost. EDITRAND will also read the names of the
- dBASE fields, their field type (like C for
- character), length and decimals and display them
- on the status line as you navigate in Edit mode.
- This switch must be used in conjunction with the
- /D switch and should appear as /DT.
-
- NOTE: Other than interpreting the header and
- record length, EDITRAND performs NO dBASE-
- intelligent operations automatically. For
- example, EDITRAND will not update the header,
- recover damaged files, or generate indexes. It is
- up to the user of EDITRAND to understand dBASE
- file structures and make the changes manually
- using EDITRAND's basic functions. The only
- exception is the use of the Update dBASE Header
- function (see page 55); with this function you can
- update the record count as held in the dBASE
- header.
-
-
- /On Create header offset. Use of this switch will
- cause EDITRAND to treat the first n bytes of the
- file as an offset header. This means that
- viewing of records will begin at byte number n +
- 1, and the first n bytes will not be visible or
- available for editing. * A denotation of this
- offset appears on line 2 of the display, just to
- the right of the Record and Field boundary status
- indicators:
-
- R:nnn-nnn F:nnn-nnn H: nnn
-
- The maximum allowable offset is the pre-edit file
- size.
-
- Ø Header offset is recorded in ER.INI.
-
- ____________________
- * If it is necessary to make changes to the header, you must
- reload the same file without the use of the /On switch.
-
-
- ----------------------------------------------------------------------
- Executing Page 9
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
-
- The above switches /D[T] and /On are mutually
- exclusive. If both switches are specified, /D[T]
- takes precedence if the loaded file has a dBASE
- structure.
-
-
-
- /Vn Video Mode. This switch can be used to force
- EDITRAND to use 25, 43 or 50 line mode. This
- switch is only valid if EDITRAND is running on a
- color monitor. Legal values for n are 25, 43, and
- 50. You must have an EGA or VGA to specify 43,
- and you must have a VGA monitor to specify 50. In
- 43 line mode, the maximum record length is 3040
- bytes, and in 50 line mode the maximum record
- length is 3600 bytes. Also, if you attempt to
- load a file whose record length is greater than
- the current maximum record length, EDITRAND will
- adjust to 43 or 50 line mode if the monitor type
- will allow it. In other words, if you are running
- in 80 X 25 mode in DOS and load a file whose
- record length is 3450 bytes, EDITRAND will attempt
- to automatically switch to 50 line mode without
- the use of the /V50 switch.
-
- /MONO Force Monochrome. EDITRAND attempts to
- automatically detect the type of monitor upon
- which it is running. However, there may be
- occasions when it is desirable to use monochrome
- color attributes even though the default monitor
- is color. For example, on a plasma screen that is
- detected as a color monitor, the combination of
- colors used may be difficult to look at; in such a
- case it may be preferable to force monochrome
- attributes. If monochrome is being used, color
- attributes can be restored by using the /MONO
- switch again.
-
- Ø Monochrome setting is recorded in ER.INI.
-
-
- Unless the /N switch is used, a backup of the edited file is
- created from which editing changes are undone and from which
- an entire edit session can be aborted. The name of the
-
-
- ----------------------------------------------------------------------
- Executing Page 10
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
- backup file is extracted from the name of the file to be
- edited - the main file name is used and given the extension
- .ERB (stands for EDITRAND Backup). In other words, if the
- file to be edited is INVENTRY.PTF, the backup created will
- be called INVENTRY.ERB. If a file by the same name already
- exists, it will be erased WITHOUT WARNING.
-
- Command line switches may be included with or without any
- other command line arguments (such as file name and record
- length). Switches remain in effect until EDITRAND is
- exited. However, switches can be changed or negated with
- the use of the Load function (see the explanation of the
- Load function on page 18). For example, if EDITRAND is
- started with the /N switch, no backups will be created for
- any files Loaded unless a new switch is specified.
-
- If neither the /N nor the /B switches is used, EDITRAND will
- not permit loading of a file with the extension ERB. In
- other words, the file PARTS.ERB cannot be edited because its
- pertinent backup file name is also PARTS.ERB.
-
- EDITRAND will attempt to create the backup file on the same
- drive and subdirectory as the target file ("target file" is
- the file that is being edited). If there is not enough disk
- space to create the backup in the target file
- drive/subdirectory, EDITRAND will then check to verify if
- the target file is on a drive other than the current default
- drive. If so, an attempt will be made to store the backup
- in the current subdirectory of the current default drive.
- This is done primarily to assist editing of large files on
- floppy disks, where insufficient disk space is available on
- the floppy disk. Be aware that this possibility exists if
- an attempt is made to restore from a backup file, as the
- desired backup may not be in the same location as the target
- file.
-
- When loading a new file, whether from the DOS command line,
- or using the Load function, you may see the message:
-
- WARNING - Last Record Truncated
-
- If this message appears, it means that the size of the
- current file is not evenly divisible by the specified record
- size, and the last physical record is not a full record. If
- the /On header offset switch was used, this could have an
-
-
- ----------------------------------------------------------------------
- Executing Page 11
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
- effect. Proceed with caution, as this is an indication that
- something may not be right - either the loaded file is not
- the file that was intended, or the correct header offset or
- record size was not used. It is possible to destroy a file
- using APPEND Record and DELETE Record in this circumstance.
-
- RELATED FILES - If a data file edited by EDITRAND has
- pertinent, separate index files or other related data files
- created by another software program, EDITRAND operations
- have no dependency or requirements for such files. If
- changes made using EDITRAND cause such an index file or
- other file to become invalid, it is the EDITRAND user's
- responsibility to re-generate indexes or make changes to
- other files outside of EDITRAND.
-
- See the Load command on page 18 for more information about
- files.
-
- Please note that throughout the remainder of this manual,
- various items are denoted with Ø. This indicates that the
- item described is saved in the initialization file ER.INI,
- to be reloaded and used the next time EDITRAND is executed.
- In summary, these items are:
-
- * File name
-
- * Record length
-
- * Header offset
-
- * Case setting
-
- * Record View setting
-
- * Tab stops
-
- * Tab increment
-
- * Field bounds
-
- * Rule line video setting
-
- * Monochrome setting
-
- * Offset display format (hex or decimal)
-
-
- ----------------------------------------------------------------------
- Executing Page 12
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
-
- * Offset shown from beginning of record or field
-
- * Prompt to purge deleted records
-
- By default, ER.INI is created in the current default
- subdirectory. This allows for multiple environments, with
- different tab settings, etc. That is, a copy of ER.INI is
- created everywhere you execute EDITRAND. However, it is
- possible to cause EDITRAND to use one, centrally located
- copy of ER.INI with the use of an environment variable. If
- you wish to take advantage of this option, include the
- following statement in your AUTOEXEC.BAT file:
-
- SET ERINIPATH=d:\mypath
-
- where d:\mypath is the full path of the subdirectory in
- which you wish EDITRAND to maintain a single copy of ER.INI.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ----------------------------------------------------------------------
- Executing Page 13
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
- BROWSE MODE
-
-
- When the program first loads into memory and displays the
- input file, the first record appears, and the program will
- be in Browse mode. Line 1 of the display contains the name
- of the current file, date and time the file was last
- modified (MM-DD-YY HH:MM:SS), size of the file versus record
- length, and current record number versus total number of
- records. For example:
-
- C:\1099INFO.DAT 05-11-88 15:36:07 | Size: 7168/128 |
- Record: 1/56
-
- If there is insufficient space for the full file path name,
- the left end of the file path name will be truncated and
- "..." will be appended. For example, if the file to be
- edited is
-
- E:\CUSTOMER\ACCOUNTS\RECVBLE\DELNQUNT\1988\MYERS.DAT
-
- it may appear as
-
- E:<>CVBLE\DELNQUNT\1988\MYERS.DAT
-
- Line 2 of the display shows Record and Field Bounds and byte
- offsets (Beginning and Ending absolute byte positions of the
- current record). For example:
-
- R:1-56 F:1-128 Beg:2817 End:2944
-
- The numbers 1-56 following R: represent the currently
- defined range of records (also referred to as record bounds)
- and the numbers 1-128 following F: represent the currently
- defined field bounds. The beginning and ending byte
- positions can be displayed in hexidecimal representation
- with the Alt-F1 function key.
-
- Line two can also display header offset if a header has been
- specified. See page 9 for a description of header offsets.
-
- The number of lines devoted to record display can vary
- according to what display mode EDITRAND is in. For example,
- in standard 80 X 25 text mode, lines 3 through 22 are used;
- in 80 X 50 mode lines 3 through 47 are used. The status
-
-
- ----------------------------------------------------------------------
- Browse Mode Page 14
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
- line (the line above the bottom line of the screen) is used
- for messages and various prompts, and the bottom line is
- used primarily for function key prompts.
-
- The data display area is set up as a set of lines depicting
- a record as broken up into contiguous 80 character segments.
- Each 80 character segment will be underlined with a rule by
- which the exact position of a particular field or byte can
- be readily ascertained. Example of a 400 byte record
- display can be seen in Figure 1, using a mock employee data
- record. Notice that the ending zero (0) of each 10 byte
- interval number will be highlighted when EDITRAND is
- executed. This is to indicate that the byte position of the
- zero is the actual ordinal position indicated by the number.
- For example:
-
- |..180....|..190..
- ^
- This position is byte 180
-
- If the record length is not a multiple of 80, then the last
- rule line will be truncated.
-
- To allow for longer record lengths, a single generic rule
- line is employed when there is not sufficient room in the
- record display area for standard rules. A generic rule has
- no numbers, only graduation marks at 5 and 10 byte
- intervals, and is located at the bottom of the record
- display area.
-
- The rules by default will appear on a blue background (black
- on a monochrome monitor). They can be made to appear
- inversely on a white background by pressing Alt-I in either
- Browse or Edit mode. See INVERSE function on page 58.
-
- No editing operations are allowed in Browse mode, but many
- other functions are available. The definitions of the
- Browse Mode functions follow.
-
-
-
-
-
-
-
-
-
- ----------------------------------------------------------------------
- Browse Mode Page 15
-
-
-
-
-
- EditRand
- ----------------------------------------------------------------------
-
-
-
-
-
-
- C:\DATA\1990\IRS.001 09-06-91 08:10:32 | Size: 227220/420 | Record: 1/541
- R: 1-541 F:51-60 H:991 Beg:1 End:420
-
- B87 COLD 4580269370